Systems and Methods for Predicting, Identifying, and/or Confirming Presence of Objects in a Predefined Space or Otherwise Associated with a Container

ABSTRACT

Systems and methods for predicting, identifying, and/or confirming the presence of an object in a predefined space include communication between the object and a sensor having a detection range. The detection range of the sensor is limited to a predefined space or direction that may be less than its maximum detection range.

RELATED APPLICATIONS

This application claims the benefit of co-pending U.S. Non-Provisionalpatent application Ser. No. 15/256,414, filed 2 Sep. 2016, and entitled“Systems and Methods for Predicting, Identifying, and/or ConfirmingPresence of Objects in a Predefined Space,” which claims a benefit tonow expired U.S. Provisional Patent Application Ser. No. 62/214,289,filed 4 Sep. 2015, and entitled “Systems and Methods for Predicting,Identifying, and/or Confirming Presence of Objects in a PredefinedSpace,” both of which are incorporated herein by reference in theirentireties.

BACKGROUND

This invention relates generally to the tracking or identification ofobjects, such as travel, work, and/or school accessories, and moreparticularly to systems and methods that may be used to review objectswithin a container and communicate with a person to inform them of thereviewed objects and/or to suggest that person place a missing objectinto the container.

Facing reality, people may at times be forgetful. Forgetfulness may becaused by any of one or more conditions, including emotional (e.g.,stress), mental (e.g., multi-tasking, distraction), chemical (e.g.,medication), and/or physiological (e.g., short-term memory loss from astroke) conditions. As a result of forgetfulness, certain object storageor transport placement may not occur. For example, when preparing totravel, a person may forget to pack an item that they intended totransport. As a further example, a person may not place items forcorrect storage at home, such as in a refrigerator, freezer, or medicinecabinet. In an attempt to ensure that objects are located appropriatelyfor a predetermined time, such as in a briefcase for a meeting, or toensure timely return of medicine to a cabinet, a person may check,double-check, and even triple-check objects that have been packed orstored or not, as the case may be.

Regarding business travel, people desire to be prepared—to haveeverything with them, to be on top of things. If objects are not packed,it may result in a feeling of failure as a person arrives at his or herdestination ill-prepared. Incomplete packing and/or storage makes forwasted trips or unnecessary purchases when a person may have to replacethe item not packed or not stored/located. Such wasted trips andunnecessary purchases are generally inefficient and result in a loss ofproductivity.

The cognitive demands of today's busy world make object tracking andorganization even more important. Therefore, the art of objectorganization and planning would benefit from improved systems andmethods of predicting, identifying, and/or confirming a presence of anobject in a predefined space.

SUMMARY OF THE INVENTION

The present invention relates to improved systems and methods ofpredicting, identifying, and/or confirming a presence of an object(item) in a predefined space or an associated container, such as a bag.

Systems and methods according to the present invention provide a virtualpersonal packing assistant that not only gives suggestions about what topack for a particular time or event, but can assist in ensuring that theplan is executed at the appropriate time. These systems and methodsutilize a user interface (e.g., an light emitting diode (LED), liquidcrystal display (LCD) (e.g., mounted in a home, such as on arefrigerator or near an exit door), heads-up display (HUD) (e.g., in avehicle), speaker, and/or buzzer) to indicate whether or not expectedobjects are represented as being located within the predefined space orassociated with a container. If not, feedback is provided on a device(e.g., mobile phone, tablet or other computer, and/or on the userinterface to see what is missing.

Systems and methods according to the present invention may be used by avariety of persons for a variety of applications. Outdoor applicationsmay include packing for a daytrip or hike, a picnic, a hunting orfishing trip, or even a mountaineering expedition. Educationalapplications may include packing for classes and/or extracurricularactivities that may change from day to day. Business applicationsinclude packing a briefcase or other bag (e.g., backpack, purse, etc.)for a day's work. Business applications may also include packing atoolbox or bag, and/or service truck for mobile job applications (e.g.,handyman, contractor, firefighter, etc.). Home applications includepacking a diaper bag, packing children's bags/lunch boxes for school,shelf or closet storage, refrigerator/freezer monitoring, and/ormedicine cabinet monitoring. Travel applications include packing asuitcase or bag for a daytrip, overnight trip, or multiple day trip to asingle destination or multiple destinations for business or leisure.Athletic applications include packing a sports bag for a practice, game,or match of a sport (e.g., hockey, baseball, soccer, lacrosse, etc.).

Programming features of embodiments according to the present inventionmay assist users by providing suggestions to a user based on usage byother people similar to the user, the user's past behavior orinstructions the user provided previously. Such systems and methods mayprovide recommendations based on packing lists created by persons otherthan the user. The systems may learn from past behavior and theassociation of products (e.g., if laptop is packed, power cord must alsobe packed). Further, such systems and methods may be aware of types ofplanned or expected activities, as well as weather forecasts, seasons,or other conditions that might influence what objects are suggested(e.g., umbrella).

Systems and methods according to the present invention may be used inconnection with a single container (such as a student's backpack) ormultiple containers (such as a briefcase and a suitcase for a businesstrip).

Systems and methods according to the present invention may employadhesive RFID labels for objects that need to be located a single timeor a few times (like copies of an exam or homework for an educationalclass) or persistent, more durable RFID tags for objects that areexpected to be tracked many more times such as a power cord of a laptopcomputer. However, adhesive RFID labels could additionally oralternatively be used on durable goods.

Systems and methods according to the present invention are not generallyrelated to locating lost objects. Instead they are directed to helpingto ensure that expected objects are located appropriately at apredefined, estimated, or predicted time.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an embodiment of a system according to thepresent invention.

FIG. 2 is a perspective view of a first embodiment of a radio frequencyidentification (RFID) tag.

FIG. 3 is a perspective view of a second embodiment of a RFID tag.

FIG. 4 is a perspective view of a plurality of RFID labels disposed on aroll.

FIG. 5 displays perspective embodiments of exemplary container types.

FIG. 6 displays perspective embodiments of exemplary objects.

FIG. 7 is a pictorial representation of an object query step of a methodaccording to the present invention.

FIG. 8 is a pictorial representation of a display step of a methodaccording to the present invention.

FIG. 9 is a flowchart of a first embodiment of a method according to thepresent invention.

FIG. 10 is a flowchart of a second embodiment of a method according tothe present invention.

FIG. 11A is an elevation view of an electronic device depicting a logindisplay according to the present invention.

FIG. 11B is the device of FIG. 11A depicting a welcome display accordingto the present invention.

FIG. 11C is the device of FIG. 11A depicting a manage account displayaccording to the present invention.

FIG. 12A is the device of FIG. 11A depicting an item display accordingto the present invention.

FIG. 12B is the device of FIG. 11A depicting an item entry displayaccording to the present invention.

FIG. 13A is the device of FIG. 11A depicting a bags display according tothe present invention.

FIG. 13B is the device of FIG. 11A depicting an attach bag displayaccording to the present invention.

FIG. 13C is the device of FIG. 11A depicting a bag entry displayaccording to the present invention.

FIG. 14A is the device of FIG. 11A depicting a configurations displayaccording to the present invention.

FIG. 14B is the device of FIG. 11A depicting a configuration entrydisplay according to the present invention.

FIG. 15A is the device of FIG. 11A depicting an events display accordingto the present invention.

FIG. 15B is the device of FIG. 11A depicting an event entry displayaccording to the present invention.

FIG. 15C is the device of FIG. 11A depicting an event bag andconfiguration entry interface according to the present invention.

FIG. 15D is the device of FIG. 11A depicting an event item entryinterface according to the present invention.

FIG. 16 is a diagram of exemplary relational associations of informationaccording to the present invention.

FIG. 17 is an alternate block diagram of an embodiment of a systemaccording to the present invention.

DETAILED DESCRIPTION

Although the disclosure hereof enables those skilled in the art topractice the invention, the embodiments described merely exemplify theinvention which may be embodied in other ways. While the preferredembodiment has been described, the details may be changed withoutdeparting from the invention, which is defined by the claims.

Turning now to the figures, FIG. 1 is a block diagram of a system 100according to the present invention. Generally, the system 100 includes acontainer 110 supporting and/or containing a sensor 112, which iscapable of detecting the presence of an object 150 or associatedidentifier 155 within a predefined space. The sensor 112, such as aradio frequency identification (RFID) receiver or reader 114, may becontrolled by a microcontroller 116. The container 110 preferably alsosupports or contains a power source, such as a battery 118, or at leasta connection to a power source, to provide electrical power to thesensor. The container 110 may further provide user communicationinterfaces 120, which may be one or more direct communication interfaces122, such as a single light emitting diode (LED), an LED display and/orpiezo buzzer, and/or indirect communication interfaces 124, such as awireless communication interface (e.g. Bluetooth, WiFi (IEEE 802.11),infrared (IrDA)), and/or a wired communication interface (not shown)(e.g., universal serial bus (USB), video graphics array (VGA),high-definition multimedia interface (HDMI)). A direct communicationinterface 122 provides information or representations of information tobe perceived directly by a person (e.g. visually and/or aurally). Anindirect communication interface 124, communicates with another device200, such as a mobile phone, tablet computer, laptop computer, displaymonitor, etc., to provide information to a person or to accessinformation data on (or receive data from) the device 200, or throughthe device 200 from an external data source 300, such as an internetserver.

As indicated, the sensor 112 is capable of detecting the presence of anobject 150 (as represented by an associated identifier 155) within afirst predefined space 112 a, which may be defined as the maximumdetection range within the capabilities of the sensor 112. Anarrangement of the sensor 112 may also be configured, as furtherexplained below, to exclude some of the first predefined space 112 a, tolimit the capability of the sensor to a second, preferably smaller space112 b, which may be substantially defined by one or more compartments ofthe container 110. Thus, while the second space 112 b is depicted asbeing outside of the container 110 for clarity, the second space 112 bis preferably substantially or completely within the container 110.

FIGS. 2-4 depict various embodiments of object identifiers (e.g., codes)155 a,b,c, such as radio frequency identification tags or labels. FIG. 2shows a first embodiment 410 of an RFID tag, which may have asubstantially rigid (e.g., substantially plastically deformable) body412 supporting an RFID circuit 415. The tag 410 may be secured to anobject 150 in a plurality of ways, such as by being adhered thereto.FIG. 3 provides a second embodiment 420 of an RFID tag, which mayinclude a more flexible (e.g., substantially elastically deformable)flap 422 supporting an RFID circuit 425. Extending preferably integrallyfrom the flap 422 may be a hitch loop 426 that can be used to secure thetag 420 to an object 150. FIG. 4 shows an embodiment 430 of a roll ofRFID labels 432 supporting an RFID circuit 435 on a flexible, preferablyadhesive-backed substrate 436, which may be covered by a releasableliner (not shown). Each successive label 432 may be removed from theroll 430, its adhesive exposed, and then secured to an object 150 by theadhesive.

FIG. 5 displays exemplary containers 110. A first container 110 a is abackpack, including a plurality of shoulder straps 160 and one or moreinterior compartments 162. A second container 110 b is a briefcase,including a single handle 164 pivotably coupled to its exterior andincluding a single interior compartment 166. A third container 110 c isa suitcase, including preferably a plurality of carry handles 168attached to its exterior and at least one interior compartment 170. Thesuitcase 110 c may further include an extendable tow handle 172 androller wheels (not shown) disposed opposite the tow handle 172. A fourthcontainer 110 d is a purse or handbag, including one or more carryhandles 174 extending from a top portion 176 of an open- or closed-topbase 178, which surrounds at least one interior compartment 180. Othercontainers 110 may include sports equipment bags (e.g., hockey equipmentbag, lacrosse equipment bag, yoga bag, weightlifting bag), insulatedcoolers (e.g., for insulating food and/or drink items, or for medicaltransport of organs, blood, or tissue), tool boxes, or household storagelocations (e.g., medicine cabinet, refrigerator, freezer, closet). Asstated above, an arrangement of a sensor 112 on a container may beconfigured to exclude some of the first predefined space 112 a, to limitthe capability of the sensor to a second, preferably smaller space 112b, which may be substantially defined by one or more compartments of thecontainer 110. This may be done by partially or substantially completelylining the desired container compartments with, or partially orsubstantially completely constructing container compartments from, aradio frequency (RF) shielding material, such as one or more of copperplated polyester, nickel/copper plated polyester, nonwoven carbonfibers, woven stainless steel (with or without other fabrics such aspolyester or cotton), silver plated nylon, and nickel/copper/cobaltplated polyester. By creating a compartment of a container 110 that islined with such material(s), and allowing the sensor 112 communicativeaccess to that lined compartment (such as by placing the sensor 112within that compartment), the detection of object identifiers 155 by thesensor 112 is limited to the desired compartment(s) of the container110. This helps prevent false positive if objects are near a container110 but not within the desired compartment thereof.

FIG. 6 shows exemplary objects 150. A first object 150 a is a laptopcomputer including a hinged display 182 coupled to a keyboard/trackpad184 and an RFID label 432 adhered thereto. A second object 150 b is acharging cable, including a first end 186 a for plugging into a powermains, a second end 186 b for plugging into an electronic device (suchas the laptop computer 150 a), and a transformer 188 disposedtherebetween. An RFID label 432 is adhered to the charging cable, suchas by being adhered to the transformer 188. A third object 150 c is abook having a cover 190 and an RFID label 432 adhered thereto, which maybe positioned to the outside or inside of the cover 190. A fourth object150 d is a notebook having a cover 192 and an RFID label 432 adheredthereto, which may be positioned to the outside or inside of the cover192. Other objects 150 may include a tablet computer, a mobile phone,sports equipment (e.g., hockey pads/helmet/gloves, lacrossepads/helmet/gloves, yoga mat/blocks/belts, weightliftinggloves/belt/chalk, shower accessories (e.g., soap container, razor,deodorant)), food and/or drink items, medical transport objects (organs,blood, or tissue), tools (e.g., hand tools, power tools, surgicalinstruments), medication containers, clothing, or household cleaners,etc. While an RFID label is shown as being adhered to the objects 150,it is to be understood that an RFID label, tag or circuit may beembedded within an object 150.

FIGS. 7 and 8 are pictorial representations of steps in a methodaccording to the present invention. FIG. 7 pictorially depicts a portionof an item or object query step and FIG. 8 pictorially depicts a portionof an alert display step. These figures will be referenced in discussionabout FIG. 10, below.

FIG. 9 is a flowchart of a first method 500 according to the presentinvention. The method 500 generally includes a set 510 of program stepsand a set 550 of processing steps. The program set 510 includes steps ofestablishing a single conditional factor or multiple conditional factorswith which to associate one or more expected objects 150, whereconditional factors are preferably associated with a scheduled event(e.g., calendar entry). The processing set 550 includes steps ofutilizing the conditional factors to identify expected objects 150 andcompare packed objects 150 present in a particular space to the expectedobjects 150 to determine whether any packed objects are missing. Theprogram set 510 generally involves human interaction and data entry, orit can be automatic, while the processing set 550 is preferablyperformed without human interaction, but may also be initiated manually.This method 500 will be explained as if the programming 510 is performedmanually and the processing 550 is performed automatically. Theprogramming 510 may be performed on a human machine interface (HMI)supported by or coupled to a container 110 and the processing 550 may beperformed by a computer system (e.g., including a microcontroller ormicroprocessor 116) communicatively coupled with the HMI and alsosupported by the container 110. Alternatively, either set of steps510,550 or individual steps thereof, may be carried out on an electronicdevice 200 in communication with a computer system supported by thecontainer.

Referring to FIGS. 1 and 9, conditional factors are programmed in one ormore steps in a method according to the present invention. In oneprogramming step 512, a conditional factor in the form of an event type(e.g. Sales Meeting, Presentation, Algebra 101, Picnic) is programmed bya user into nonvolatile memory to be accessed by the microcontroller116. The memory may be local (e.g. supported by the container 110) orremote (e.g. on a mobile phone 200). In another programming step 514, aconditional factor in the form of a location (e.g. Coffee Shop, ClientName/Address, Jones Hall Rm 303, City Park) may be programmed by a userinto nonvolatile memory (preferably the same nonvolatile memoryhardware) to be accessed by the microcontroller 116. Either or both ofthe first programming step 512 and the second programming step 514 maybe undertaken. Another programming step 516 involves the association ofexpected items or objects 150 with the programmed event type and/orlocation conditional factors, or other conditional factors previously orlater programmed or analyzed. That is, the programming steps do not havea particular order. The programming into nonvolatile memory creates arelational database to be used to provide functionality according to thepresent invention.

Expected items or objects 150 may be predefined individually in listsaccording to event types or other conditional factors (e.g. location) orobjects may be specified uniquely by a user, or a combination of thetwo. In any event, the result of the programming steps 510 is anassociation of expected objects 150 with conditional factors. Thisassociation may be represented in tablature form as shown in Table 1.

TABLE 1 Conditional Factors Event Type: Sales Meeting Hockey PracticeLocation: XYZ Corp. <null> or nonexistent Associated Expected ObjectLists Object 1: Laptop computer SkateLeft Object 2: Laptop power cordSkateRight Object 3: Presentation remote control GloveLeft Object 4:Business cards GloveRight Object 5: XYZ Corp. File KneePadLeft Object 6:LCD Projector KneePadRight Object 7: Product Samples ShoulderPads Object8: <null> or nonexistent ElbowLeft Object 9: <null> or nonexistentElbowRight Object 10: <null> or nonexistent Breezers Object 11: <null>or nonexistent Helmet Object 12: <null> or nonexistent Jersey Object 13:<null> or nonexistent SockLeft Object 14: <null> or nonexistentSockRight Object 15: <null> or nonexistent ProtectiveCupThere may be a fixed number of expected objects associated with eachconditional factor, but it is preferred to have a variable number ofexpected objects selected from a master expected object list, to avoidduplication of programming steps. In other words, from a master expectedobject list, a hash may be created from the conditional factors (e.g.,event type, location, etc.), and from that hash, expected objects arepreferably selected from the master expected object list.

Additionally or alternatively, other conditional factors may be used andassociated with items or objects 150, where such factors are predefinedor defined by a user. At least one, but preferably all conditionalfactors for a particular scheduled event are utilized to generate anexpected object list. In this fashion, greater resolution is providedfor a scheduled event, and more tailored expected object lists may begenerated. Alternatively, fewer than all conditional factors for aparticular scheduled event may be used, because in certain situations, auser may not have all the information necessary to establish a completeconditional factor set.

To use the conditional factors and associated expected objects, theprocessing steps 550 are executed. In one step 522, a scheduled event isidentified, such as by querying a calendar. This query may be manual orautomatic, such as by analyzing a server-maintained calendar (e.g.,Outlook®, Google®) or a local electronic calendar (e.g., Windows®,Android®). A calendar event is identified and one or more conditionalfactors are parsed 554 to query (i.e. identify) expected objects 556 aassociated with the parsed conditional factors. Additional conditionalfactors may be queried 556 b and/or parsed from a calendar event toarrive at an expected object list. An object space 112 b having beenpredefined, a determination is then made of packed objects present inthe predefined space 112 b, as represented by the presence of respectiveassociated identifiers 155, to arrive at a packed object list. Theexpected object list is then compared 560 against the packed object listto determine if the objects included on each list match. If all objectson the expected object list are included in the packed objects list,then an acknowledgement or confirmation is displayed 562 to a user andthe process is complete. If all objects on the expected object list arenot included in the packed objects list, then an alert is displayed to auser, and the process will return to regenerate the packed object list.The regeneration of the packed object list can be performedautomatically after a predetermined delay time or can be manuallyinitiated (e.g., by pushing a button) after additional objects have beenplaced into the predefined space.

While the method 500 is primarily concerned with identifying objectsthat are missing from a predefined space at a predetermined (or manuallyactivated) time, the method may optionally include a step or sub-steproutine to inform a user if the packed object list includes items thatare not on the expected object list. In other words, a two-waycomparison between the expected object list and packed object list iscontemplated.

Also, certain steps 552,554,556 may be simplified in situations where apredefined space is to be analyzed for particular contents periodicallyor manually. For instance, in certain home or medical situations, if amedicine cabinet, for example, is to be monitored, the packed objectlist may be generated periodically at a predetermined interval (e.g.,every minute, hour, day, week, month, year, or plurality of any ofthese) and the comparison with the expected object list occurring atsubstantially the same interval. If the comparison 560 indicates thatobjects are missing, an alarm may sound.

FIG. 10 is a flowchart of a second method 600 according to the presentinvention. This method 600 generally includes a set 610 of program stepsand a set 650 of processing steps. The program set 610 includes steps ofestablishing a single conditional factor or multiple conditional factorswith which to associate one or more expected objects 150, whereconditional factors are preferably associated with a scheduled event(e.g., calendar entry). The processing set 650 includes steps ofutilizing the conditional factors to identify expected objects 150 andcompare packed objects 150 present in a particular space to the expectedobjects 150 to determine whether any packed objects are missing. In thismethod 600, both the program set 610 and the processing set 650 of stepsare executed largely automatically, though they may be initiatedmanually. Indeed, the processing set 650 of steps is at leastsubstantially similar or identical with the processing set 550 of thefirst method 500 discussed above. However, unlike the program set 510 ofthe first method 500, the program set 610 of this method is undertakensubstantially automatically, though it may be initiated manually. Theprogramming 510 may be performed on a human machine interface (HMI)supported by a container 110 and the processing 550 may be performed bya computer system (e.g., including a microcontroller or microprocessor116) communicatively coupled with the HMI and also supported by thecontainer 110. Additionally or alternatively, either set of steps510,550 or individual steps thereof, may be carried out on an electronicdevice 200 in communication with a computer system supported by thecontainer.

In this method 600, an expected object list is created at a request of auser that has packed objects into the predefined space. In other words,a user has manually confirmed the presence of desired objects to beassociated with one or more conditional factors. Upon initiating theprogram set 610, conditional factors are automatically logged, such asby querying 612 a user's calendar and logging conditional factors, suchas an event type 614 and/or a location 616. Other or alternative typesof conditional factors may be predetermined, such as current or futurepredicted weather conditions at the location that has been logged, timeof year, local national holidays at the location, etc. In a scanningstep 618 (such as with the RFID reader 114), the objects that have beenplaced into the predefined space will be logged, and an expected objectlist will be generated. This expected object list will be used by theprocessing set 650 at future times when the respective conditionalfactors are satisfied. The automatic program set 610 may be repeatedmultiple times (manually or automatically) to modify expected objectlists associated with conditional factors, thereby “learning” objectpacking behavior of a particular user.

It may also be advantageous to monitor contents of a container 110 in a“locked” mode, where that container is to be left, in a potentiallyunsecure place for example. In such situation, a manual scan (e.g., 618)may be initiated so that the contents of the container 110 are learnedand an expected object list is generated. A manual scan of each object150 to be associated with a container 110 may also be performed. Afterthe contents are learned, scanning (e.g., 658) and comparing (e.g. 660)may be automatically performed at periodic intervals, eithercontinuously or upon the occurrence of an event or continuously for apredetermined time upon the occurrence of an event. For instance, a userdecides to leave a container 110 in an unoccupied hotel room or baggagecheck, into which hotel staff may have access. Prior to leaving thecontainer 110, the user may ensure desired contents are in the container110 and the scan may be manually initiated to virtually “lock” thecontainer 110. While the user is away from the container 110, thescanning (e.g., 658) and comparing (e.g. 660) may be automaticallyperformed at periodic intervals, such as one scan and one compare everyhour or multiple thereof, every minute or multiple thereof, or everysecond or multiple thereof. The automatic scanning may alternatively beinitiated by an occurrence of an event, such as movement of thecontainer 110 (e.g. causing movement of an accelerometer), and theautomatic scanning and comparing may thereafter execute once, aplurality of predetermined times, or continue periodically. The resultsof any comparison resulting in a mismatch between the expected objectlist and the scanned object list are logged in electronic memory carriedby the container 110 after each mismatch and/or transmitted to the user,either realtime (if the container 110 is communicatively coupled to acommunications network) or when the user and container 110 are reunited.The log entry of a mismatch may include information such asidentification of mismatched object(s), time of day of mismatch,duration of mismatch, and location (geographic or otherwise) ofcontainer at time of mismatch.

A representative electronic device 200 with a user interface 1010 of asoftware application is shown in FIGS. 11A-15D. That is, the userinterface 1010 includes a display of information, suggestions, userprompts, and/or instructions, and interactive options for a user of theelectronic device 200. Interactive options may be provided as virtualpushbuttons, such as images displayed on a capacitive display screen(touch screen) to be selected with a user's finger or a stylus, or assoft buttons associated with physical pushbutton switches on the device200. FIG. 11A provides a login display 1100, including a username prompt1102, a password prompt 1104, and a login virtual pushbutton 1106. Theprompts 1102,1104 are preferably capable of receiving text entry, suchas from a QWERTY keyboard displayed on the interface after one of theprompts is selected. After a user has entered a combination of ausername and associated password (the correct combination(s) of whichmay be stored locally on the device 200 or remotely on a datastoreaccessible over a network by the device 200), the login pushbutton 1106may be selected, the combination verified against correct combinations,and access to the application may be allowed after confirmation of entryof a correct combination. Additionally or alternatively, a biometricconfirmation, such as an electronic fingerprint analysis or iris scan,may be used to log in.

Upon entry of a correct username and password combination or biometricidentification, and login confirmation, a Welcome display 1110 may bepresented to the user, as shown in FIG. 11B. This display 1110 may serveas a homescreen, from which various aspects of the application may beviewed and/or managed. Preferably, the Welcome display 1110 includes anevent list 1120 and an option list 1130. The event list 1120 includesone or more displayed event entries 1122, such as only the nextchronologically scheduled event, or a day's scheduled event(s). Eachevent entry 1122 preferably includes an associated event name 1124,date/time 1126, and event status indicator 1128. The event name 1124 anddate/time 1126 are created or selected by a user in an event creationprocess, described more fully below. The event status indicator 1128provides a visual indication of whether or not all required items arepacked in a particular container for the event. The event statusindicator 1128 is preferably a color coded shape, with a first color(e.g., green) indicating that the device 200 is in communication with acontainer 110, and items associated with defined container configurationhave been scanned and/or packed in the container 110. A second color(e.g., orange or yellow) may indicate that the device 200 is incommunication with the container 110, but one or more items have notbeen scanned and/or packed in the container 110 according to apredefined configuration. A third color (e.g., red) indicates that thecontainer associated with the particular event is not in communicationwith the device. Any portion of an event entry 1122 may be selectable bya user, such as being provided as a hyperlink or otherwise, to enable auser to navigate to an event display 1500, as shown in FIG. 15b , andfurther described below. Preferably, every display (interface) that isprovided after a user has successfully logged in includes a top levelmenu virtual pushbutton 1101. Upon selection of this option 1101, avariety of other selections may be displayed for the user, such as“Home” to return to the Welcome display 1110 and/or any one or more ofthe option list options 1130 from the Welcome display 1110.

The option list 1130 on the Welcome display 1110 preferably includes aplurality of virtual push buttons providing a user with options to viewand configure the application. Preferably, there are four options: anItem management option 1132, a Bag management option 1134, aConfiguration management option 1136, and an Event management option1138. Further, there is preferably an Account management option 1140 anda Help option 1142. Selection of the Item management option 1132preferably navigates a user to an Items display 1200, as shown in FIG.12A. Selection of the Bag management option 1134 preferably navigates auser to a Bags display 1300, as shown in FIG. 13A. Selection of theConfiguration management option 1136 preferably navigates a user to aConfigurations display 1400, as shown in FIG. 14A. Selection of theEvent management option 1138 preferably navigates a user to an Eventsdisplay 1500, as shown in FIG. 15A. Selection of the Account managementoption 1140 may navigate a user to a Manage Account display 1150, suchas that shown in FIG. 11C. Selection of the Help option 1142 preferablynavigates a user to a Help display (not shown), which may provide anindex or descriptions of application operability, such as the managementsteps described herein.

The Manage Account display 1150, shown in FIG. 11C, provides a userinterface to allow a user to associate various personal information 1152with his or her account in the application on the device 200. Suchinformation 1152 may include a password (with confirmation), the user'sfirst and last name, and contact information, such as email address,physical address (e.g., postal address) including a street, city,state/province, and postal code. An Update virtual pushbutton 1154 maybe provided to enable the user to synchronize the information providedon this display 1150 with a remote server over a communications channel.

FIG. 12A depicts an embodiment of an Item display 1200, which may bedisplayed after the Item management option 1132 on the Welcome display1110 is selected. Through this display 1200, a user is able to view andadd items, which may eventually be associated with a particularcontainer (e.g., bag) in a particular configuration. The Item display1200 preferably includes an Add Item virtual pushbutton 1202, and atleast one inventory list 1210, which may be divided into a permanentinventory list 1212 and a temporary inventory list 1214. The inventorylist 1210 includes item entries 1216, each item entry 1216 including anitem name 1218 and an item status 1220. The item name 1218 is created orselected by a user in an item creation process, described more fullybelow. The item status indicator 1220 is preferably a color coded shape,with a first color (e.g., green) indicating that the device 200 is incommunication with a container 110, and the respective item isassociated with a defined container configuration and has been scannedand/or packed in the container 110. A second color (e.g., red) mayindicate that the respective item has not been associated with acontainer 110 that is in communication with the device 200. A thirdcolor (e.g., black) indicates that the respective item is not yetassociated with an RFID tag 155. Any portion of an item entry 1216 maybe selectable by a user, such as being provided as a hyperlink orotherwise, to enable a user to navigate to an item entry display 1250,as shown in FIG. 12B, and further described below.

If the Add Item pushbutton 1202 is selected by a user, an item entrydisplay 1250 is presented, as shown in FIG. 12B. In this interface, auser may change or enter a name of an item (“Cap” in this embodiment),and an optional photo entry field 1252 may be displayed along with atextual description 1254 of the item, which may be edited by the user.By selecting the photo entry field 1252, the user may be prompted toeither capture a photograph using a camera provided on the device 200,or to select a photograph from a photo storage location (e.g., theuser's photo gallery on the device 200 or synchronized remote server).An inventory type indication 1256 may be displayed to convey whether theitem is permanent inventory or temporary inventory, and an associatedconfiguration list 1258 may be displayed. The configuration list 1258simply displays a listing of configurations that have been associatedwith the respective item, such as through selection(s) made in the itemlist 1458 in the configuration entry display 1450 of FIG. 14B. As usedherein, a “permanent” item is generally understood to be an item that islikely to be used multiple times, perhaps for different events,configurations, and/or containers. As used herein, a “temporary” item isgenerally understood to be an item that is likely to be used only asingle time, or sporadically, and therefore is not intended to begenerally repeatedly associated with a particular type of event,configuration, or container. Preferably, the items to be entered fromthe item entry display 1250 accessed from the Item display 1200 are onlypermanent items. Temporary items are preferably added by a user directlyto a particular event, and are not associated with future events unlessmanually added to such future event. Further options to delete 1260 theitem from the application or to update 1262 the item's information(e.g., save the changes) are provided. The delete functionality 1260 isprovided preferably only for permanent inventory items and temporaryitems are preferably removable only from within a particular event, asexplained below. Finally, a “back” option 1264, which will return a userto the Item display 1200 without saving any changes, such as when a useraccesses the item entry display 1250 for reference.

FIG. 13A depicts an embodiment of a Bags display 1300, which may bedisplayed after the Bag management option 1134 on the Welcome display1110 is selected. The Bag display 1300 generally includes a containerlist 1310 and an Add Bag virtual pushbutton 1312. The container list1310 includes bag entries 1314, each bag entry 1314 including a bag name1316 and a bag status 1318. The bag name 1316 is created or selected bya user in a bag entry process, described more fully below. The bagstatus indicator 1318 is preferably a color coded shape, with a firstcolor (e.g., green) indicating that the device 200 is in communicationwith the respective container 110. A second color (e.g., red) mayindicate that the respective container has been paired with the device(e.g., Bluetooth pairing) and associated with the software application,but the container is not currently connected (e.g., out of communicationrange, container communication device powered off, device 200communications powered off). A third color (e.g., black) indicates thatthe respective container is not yet associated with the device 200 andsoftware application. Any portion of a bag entry 1314 may be selectableby a user, such as being provided as a hyperlink or otherwise, to enablea user to navigate to a bag entry display 1350, as shown in FIG. 13C,and further described below.

If a user selects the Add Bag option 1312 from the Bags display 1300, anAttach Bag display 1330 may be presented, as shown in FIG. 13B. Fromthis display 1330, a user may attempt to place the device 200 incommunications with a container 110, or opt to add a container 110. Thisdisplay 1330 provides a container list 1332, an Attach option 1334, anda Back option 1336. The container list 1332 includes entries eachincluding a bag name 1338, upon user selection of which initiates acommunication pairing process between the device 200 and the selectedcontainer 110, such as a Bluetooth pairing process, as that process isunderstood in the art, or other establishment of a communicationchannel, such as through a handshake protocol. If the user desires toadd a new bag to communicate with, the user may select the Attach option1334, which may then result in the presentation of the bag entry display1350, as shown in FIG. 13C. Alternatively, a user may return to the Bagsdisplay 1300 by selecting the Back option 1336.

FIG. 13C depicts a bag entry display 1350, which may be accessed throughinteraction on the Bags display 1300 or the Attach Bag display 1330,previously discussed. In this interface, a user may change or enter aname of a container (“Backpack” in this embodiment), and an optionalphoto entry field 1352 may be displayed along with a textual description1354 of the item, which may be edited by the user. By selecting thephoto entry field 1352, the user may be prompted to either capture aphotograph using a camera provided on the device 200, or to select aphotograph from a photo storage location (e.g., the user's photo galleryon the device 200 or synchronized remote server). An associatedconfiguration list 1358 may also be displayed. The configuration list1358 simply displays a listing of configurations that have beenassociated with the respective container, such as through selection(s)made in the container list 1456 in the configuration entry display 1450of FIG. 14B. A bag status 1318, indications of which have beenpreviously described, may be provided as a virtual pushbutton, which mayinitiate or facilitate a communication pairing functionality between thedevice 200 and the indicated container 110. Additionally oralternatively, such pushbutton may be used to provide access for a userto change communications settings (e.g., Bluetooth settings) Furtheroptions to delete 1360 the container from the application or to update1362 the container's information (e.g., save the changes) are provided.Finally, a “back” option 1264, which will return a user to the Bagsdisplay 1300 without saving any changes, such as when a user accessesthe bag entry display 1350 for reference.

FIG. 14A depicts an embodiment of a Configurations display 1400, whichmay be displayed after the Configuration management option 1136 on theWelcome display 1110 is selected. The Configurations display 1400generally includes a configuration list 1410 and an Create Configurationvirtual pushbutton 1412. The container list 1410 includes bag entries1414, each bag entry 1414 including a configuration name 1416. Theconfiguration name 1416 is created or selected by a user in aconfiguration entry process, described more fully below. Any portion ofa configuration entry 1414, such as the configuration name 1416, may beselectable by a user, such as being provided as a hyperlink orotherwise, to enable a user to navigate to a configuration entry display1450, as shown in FIG. 14B, and further described below.

FIG. 14B depicts an embodiment of a configuration entry display 1450,including a configuration name 1452 (“Practice Clothes” in this case)and configuration description 1454, both of which may be textuallyedited by a user. A bag selection list 1456 and an item selection list1458 are provided to enable a user to combine one or more items from theitem selection list 1458 with one or more bags from the bag selectionlist 1456. The bag selection list 1456 is preferably populated withcontainer names entered by a user through the bag entry display 1350.Preferably, the bag selection list 1456 includes a selection 1457 whichindicates indifference to which container is to be used in theconfiguration. The item selection list 1458 is preferably populated withitem names entered by a user through the item entry display 1250, whichare preferably permanent items. Further options to delete 1460 theconfiguration from the application or to update 1462 the configurationinformation (e.g., save the changes) are provided. Finally, a “back”option 1464, which will return a user to the Configurations display 1400without saving any changes, such as when a user accesses the bag entrydisplay 1450 for reference. Once a configuration has been established,it can be assigned to a particular event, to be explained below.

FIG. 15A depicts an embodiment of an Events display 1500, which may bedisplayed after the Event management option 1138 on the Welcome display1110 is selected. This display 1500 preferably includes at least oneevent list, but more preferably a plurality of event lists. Event listsmay include at least one of a next event list 1510, a scheduled eventlist 1512 and/or an unscheduled event list 1514. The Events display 1500preferably further includes a Create Event virtual pushbutton 1520. Eachevent list includes event entries 1511, each event entry 1511 includingan event name 1513, an event schedule 1515, and an event statusindicator 1517. The event name 1513 is created or selected by a user inan event creation process, described more fully below. The eventschedule 1515 indicates whether or not the event has been scheduled, andif so, the date, day, and/or time of the event. If the event is notpresently scheduled, the event schedule 1515 may be selectable (e.g.,hyperlinked) to allow the user to add the event to his or her calendar,which may be a calendaring software application resident on the device200. The event status indicator 1517 is preferably a color coded shape,with a first color (e.g., green) indicating that the device 200 is incommunication with a container 110, and items associated with definedcontainer configuration have been scanned and/or packed in the container110. A second color (e.g., orange or yellow) may indicate that thedevice 200 is in communication with the container 110, but one or moreitems have not been scanned and/or packed in the container 110 accordingto a predefined configuration. A third color (e.g., red) may indicatethat the container 110 associated with the particular event is not incommunication with the device 200. Any portion of an event entry 1511may be selectable by a user, such as being provided as a hyperlink orotherwise, to enable a user to navigate to an event entry display 1530,as shown in FIG. 15B, and further described below.

FIG. 15B depicts an event entry display 1530 according to the presentinvention. In this interface, a user may change or enter a name 1532 ofan event (“Practice” in this embodiment), and an optional date entryfield 1534 may be displayed along with a textual description 1536 of theevent, which may be edited by the user. By selecting the date entryfield 1534, the user may be prompted to either enter a date and time toschedule the event, or to select a date and time from a graphicalrepresentation of a calendar (e.g., a date/time picker). Alternatively,the user may be presented with a list of events that have already beenscheduled in another software application, such as a calendaringapplication, and the user may select an event from such list toassociate containers, configurations, and items therewith. A Bags andConfigurations list 1538 is provided, with each list entry including aname 1538 a and a status 1538 b. Selection of a Bag and Configurationlist entry will associate a particular container 200 and configuration(having been entered by a user on the configuration entry display 1450of FIG. 14B) with the particular event being created or edited in thisdisplay 1530. If a desired container/configuration pair is not providedin the Bags and Configurations list 1538, a user may opt to create sucha combination by selecting an Attach bag and configuration virtualpushbutton 1545, which may navigate the user to a Bag and Configurationdisplay 1550 shown in FIG. 15C. The status 1538 b is preferably a colorcoded shape, with a first color (e.g., green) indicating that the device200 is in communication with a container 110, and items associated withthe defined container configuration have been scanned and/or packed inthe container 110. A second color (e.g., orange or yellow) may indicatethat the device 200 is in communication with the container 110, but oneor more items have not been scanned and/or packed in the container 110according to the predefined configuration. A third color (e.g., red)indicates that the container associated with the particular event is notin communication with the device 200. The event status 1517 may beinherited directly from the status 1538 b associated with a particularcontainer/configuration pair.

An event item list 1540 is also provided in this display 1530. This list1540 sets forth the items that are required to be associated with aparticular container 110 to successfully complete an event verificationprocess, as described above. The item list 1540 is populated with itemnames 1540 a and associated item status indicator 1540 b (e.g., itemstatus indicator 1220, as previously described). The item list 1540 ispopulated with items extracted from a selected, predeterminedconfiguration and/or temporary items added for a particular event only.Temporary items may be associated with a particular event by enteringinformation through an event item entry interface 1570, as shown in FIG.15D, which may be accessed through this display 1530 by selection of anAdd Item virtual pushbutton 1547. Further options to delete 1542 theevent from the application or to update 1544 the item's information(e.g., save the changes) are provided. The delete functionality 1542 isprovided preferably to remove an event from this respective softwareapplication only, and not to remove the event from any other calendaringsoftware provided on the device 200. Finally, a “back” option 1546,which will return a user to the Events display 1500 without saving anychanges, such as when a user accesses the event entry display 1530 forreference.

FIG. 15C depicts an event bag and configuration entry interface 1550according to the present invention. This interface 1550 provides acontainer list 1552 and a configuration list 1554. A container 110 maybe added to an event without an associated configuration so that itemscan be associated with a particular container for the event. If aconfiguration is also selected from the configuration list 1554 to beassociated with the event, then all of the items from that configurationare associated with the event, and will be displayed in the item list1540 upon saving changes and returning to the event entry display 1530.To exit this display 1550, without associating any container orconfigurations with the event, a Remove virtual pushbutton 1556 may beselected by a user. To save the selected container and optionalconfiguration, an Attach virtual pushbutton 1558 may be selected by theuser. In either event, the user is returned to the event entry display1530 of FIG. 15B.

FIG. 15D depicts an event item entry interface 1570 according to thepresent invention. This interface may be accessed by selecting the AddItem virtual pushbutton 1547 from the event entry display 1530, and isused primarily to associate a temporary item with the event beingentered. In this interface, a user may change or enter a name of atemporary item (“Signed release form” in this embodiment), and anoptional photo entry field 1572 may be displayed along with a textualdescription 1574 of the item, which may be edited by the user. Byselecting the photo entry field 1572, the user may be prompted to eithercapture a photograph using a camera provided on the device 200, or toselect a photograph from a photo storage location (e.g., the user'sphoto gallery on the device 200 or synchronized remote server). Furtheroptions to delete 1576 the item from the event (i.e., dissociate theitem from the event) or to update 1578 the event information (e.g., savethe changes) are provided. Finally, a “back” option 1580, which willreturn a user to the event entry display 1530 without saving anychanges.

FIG. 16 is a diagrammatic representation of exemplary relationshipsbetween the data constructs in a software application on a mobile device200 according to the present invention. As can be seen, the applicationmakes possible one-to-one, many-to-one and many-to-many relationshipsbetween items and configurations. Further, there is possible one-to-one,many-to-one and many-to-many relationships between configurations andcontainers 110 (i.e., bag). Such relationships and functionality may beachieved by a relational database, including a plurality of tables ofdata, such as an item table, a container table, a configuration table,and an event table. In this manner, one or more items can be associatedwith a particular event and/or with a particular configuration. One ormore containers may be associated with a particular configuration. Oneor more configurations may be associated with a particular event.

FIG. 17 is a diagrammatic representation of a system 100 according tothe present invention, similar to that of FIG. 1. FIG. 17 furtherdepicts a mobile device datastore in the form of a mobile devicedatabase 220, which may be populated from an external data source 300upon a successful user login, as described above. Further, FIG. 17identifies a possible external data source 300 comprising a cloud serverarrangement, including its own datastore and network accesscapabilities.

The foregoing is illustrative only of the principles of embodimentsaccording to the present invention. Modifications and changes may occurto those skilled in the art, so it is not desired to limit the inventionto the exact disclosure herein provided. For instance, the display orinterface naming conventions used herein are not limiting. Further,while a primary embodiment has been described as utilizing a databaseresident in memory on a mobile electronic device separate and apart froma container, it is to be understood that a respective schedule orcontainer configuration could be pushed to a particular container andthe event information and status may be displayed on the container,itself, such as through a user interface provided thereon. While thepreferred embodiment has been described, the details may be changedwithout departing from the invention, which is defined by the claims.

We claim:
 1. A method for packing objects in a container, the methodcomprising steps of: providing a container; providing a code readerassociated with the container; providing a microcontroller; providing amemory storage accessible to the microcontroller; programming aconditional factor stored within the memory storage; storing an expectedobject list in the memory storage; associating the expected object listwith the conditional factor; identifying a scheduled event; associatingthe conditional factor with the scheduled event; providing an object;providing a code associated with the object, the code being recognizableby the code reader; recognizing the code of the object within thecontainer; assembling a packed object list comprising the object forwhich the code associated with the object was recognized by the codereader; and comparing the expected object list with the packed objectlist.
 2. The method of claim 1 further comprising the step of notifyinga user when the packed object list is the same as the expected objectlist.
 3. The method of claim 1 further comprising the step of notifyinga user if the packed object list is not the same as the expected objectlist.
 4. The method of claim 1 further comprising the steps of:providing a handheld electronic device with a user interface displaycapable of communications with the code reader; pairing the handheldelectronic device with the code reader; providing a status indicator ofthe communication between the handheld electronic device and the codereader on the handheld electronic device; and displaying at least one ofthe condition factor, the expected object list, or the packed objectlist on the user interface display.
 5. The method of claim 4, whereinthe communications comprise wireless communications.
 6. The method ofclaim 4, wherein the user interface display is presented through acapacitive touch screen capable of receiving input from a touch of ahuman finger.
 7. The method of claim 4, wherein the status indicator isa color comprises a first color when the handheld electronic device iscontemporaneously not in communication with the code reader; the colorcomprises a second color when the handheld electronic device iscontemporaneously in communication with the code reader and the code hasnot been recognized by the code reader; and the color comprises a thirdcolor when the handheld electronic device is contemporaneously incommunication with the code reader and the code has been recognized bythe code reader.
 8. The method of claim 7, wherein the first, second andthird colors are distinct colors.
 9. The method of claim 7, wherein thefirst color is red.
 10. The method of claim 7, wherein the second coloris selected from the group consisting of yellow and orange.
 11. Themethod of claim 7, wherein the third color is green.
 12. The method ofclaim 1 further comprising the step of regenerating the packed objectlist.
 13. The method of claim 12, wherein the regeneration of the packedobject list is automatic after a predetermined delay time.
 14. Themethod of claim 1, wherein the conditional factor is an event type. 15.The method of claim 1, wherein the conditional factor is an eventlocation.
 16. The method of claim 1, wherein the container is selectedfrom the group consisting of: a backpack, a briefcase, a purse, a sportsduffel bag, and a suitcase.
 17. The method of claim 1, wherein the codereader comprises a radio frequency identification (RFID) reader.
 18. Themethod of claim 17, wherein the code comprises a radio frequencyidentification (RFID) code.
 19. The method of claim 1, wherein the codereader is physically secured to the container.